Ticket Management

OBJECTIVE

The Ticket Management option is used to import receivable tickets and to check and correct these tickets. This option is also used to enter a ticket manually.

 

PREREQUISITES

 

ICONS

ClosedTicket Management option icons

Icons

Title

Used to

Display Only Non-transferred Entries

Filter the entries to display only the ones that have not been transferred yet.

Display Only Transferred Entries

Filter the entries to display only the ones that have been transferred.

Display Non-transferred TR Transactions

Filter the transportation transactions to only display the ones that have not been transferred yet.

Display Transferred TR Transactions

Filter the transportation transactions to only display the ones that have been transferred.

Pending Transactions

Display the Quarry Tickets Pending Transaction’s contents grid. For more information, consult the Create a Ticket from a Pending Transaction section.

Recalculate Unit Price

Forces the recalculation of the unit price.

Tools

Access the Ticket Import window.

By clicking the dropdown menu, it is possible to access other options:

  • Hours – Allows the user to indicate the date, the number of hours worked as well as the invoice number;
  • TR Conversion – Used to indicate the transport status (to the Source and Destination, Entry, On Hold or Non chargeable);
  • Mat Conversion-Receivable – Used to indicate the material status (to the Source and Destination, Entry, On Hold or Non chargeable);
  • Mat Conversion-Payable – Used to indicate the material status (to the Source and Destination, Entry, On Hold or Non chargeable);
  • Supplier Conversion TR – Used to indicate the adjustment date and the supplier code.

Inventory Inquiry

Access the Inventory Inquiry window.

Mass Change

Modify a great number of tickets.

Mass Deletion

Delete a great number of tickets.

Only the icons specific to this window are defined in the table below.

 

Summary

 

PROCEDURE

 

maestro* > Tickets > Quarry Tickets > Processing > Ticket Management

 

Import tickets

  1. Configure the default manufacturer and file location.

 

The default manufacturer can be specified in Configuration or, if a source configuration is required, in the project, in Project Management.

  1. Click the Tools icon and select Import.

Field

Description

Source

Source of the tickets.

NOTES: If the invoicing project entered in Configuration contains “X” characters, they are used as default values.

Selection of the source depends on the project type or the first letter of the invoicing project configured in Configuration.

Manufacturer

Developer of the software that generated the import file. This value is displayed automatically, based on the value entered in Project Management and Configuration.

NOTE: The technical specifications for each of the developers are included in the appendix.

Filename

Location and name of the file to be imported. A default value can be entered in Project Management and Configuration.

Transaction Date

Used as the default ticket entry date. The default value is the working date.

  1. Select the file to be imported in Filename.
  2. Enter the Transaction Date.

The Import Multiple Source check box is displayed only if the selected manufacturer is « WEM » or « Integra ». This functionality is not available for other manufacturers. It allows you to import quarry tickets for many sources at the same time (in Ticket Management, the source is equivalent to a project).

For manufacturers « WEM » or « Integra », the External Source column will also be displayed in the import grid.

  1. Click the Refresh icon to load the selected file in the Closedimportation grid.

Field

Description

Line

Ticket line number.

Message

Error message, if applicable.

Import

Used to import the ticket.

NOTES: If the box is checked, maestro* validates and imports the ticket.

If it detects that the ticket is already in maestro*, it automatically clears the box.

Source

Source of the ticket; project.

Ticket No.

Ticket number.

NOTE: In maestro*, this number is unique and represents the quarry.

Estimate Number

Number of the estimate made to the customer.

Date

Date the ticket was created.

NOTE: Maestro* uses this date to calculate the discounts defined in the Customer Discount Table.

Customer Project

Project number.

NOTES: The customer’s project number for a ticket with the Receivable Invoicing Type.

The project can affect grouping on the invoice. The group is defined in Configuration.

The project determines whether the Invoicing Type of the ticket is Internal or not.

Contract

Contract number or for the bid to the customer.

Expense Activity

Expense activity for the Internal and Payable tickets.

NOTE: The default value is the Expense Activity defined in Catalogue Management.

Product Code

Product code defined in Catalogue Management.

Description

Description of the product code.

File Code

Customer code or supplier code according to the Invoicing Type.

NOTE: For a Receivable ticket, the customer code can be received as an External Code defined in Customer Management.

Invoicing Type

Used to determine whether the ticket is for the input or output of product, which means whether the ticket is Receivable or Payable.

NOTE: Only some manufacturers support Payable tickets.

P.O.

Purchase order number.

NOTE: The purchase order number is used when maestro* applies the discounts defined in the Customer Discounts Table.

Customer P.O.

Customer purchase order number.

NOTE: The Customer P.O. is used for grouping on the invoice.

Quantity

Quantity of product invoiced.

Unit

Product unit.

Sale UP RM

Unit price of the product.

NOTE: This value can be changed by maestro* if it applies discounts. The Product Pricing Source configuration in Configuration – Quarry Tickets is used to manage the source of prices.

Product Amount

Total amount of the product.

Truck Number

Truck number from Define Trucks.

NOTE: The truck number is only validated if the Carrier type is Hired Trucker.

Description

Description of the truck.

Carrier type

Carrier type. The choices are Hired Trucker or Customer Driver.

NOTE: The choice should be Hired Trucker if there is a calculation for transportation. Otherwise, the choice should be Customer Driver.

Region

Source or destination region of the product.

NOTE: The Do not validate the region during import option in ConfigurationQuarry Tickets (Import section) prevents maestro* from validating the region.

Description

Description of the region.

Sale Quantity TR

Quantity invoiced for the receivable transportation.

NOTE: This quantity is only displayed if the Carrier type is Hired Trucker.

Sale UP TR

Unit cost of receivable transport.

NOTE: This value can be changed by maestro* if it applies discounts. The Transport options in Configuration are used to manage the source of prices.

Sale amount TR

Sales amount for the receivable transport.

KM

Number of kilometers covered.

NOTE: When maestro* posts the payable transportation, transportation by hour prevails over transportation by kilometer.

Time

Delivery time. This field is used for information purposes only.

Hours

Number of hours of transport.

NOTE: When maestro* posts the payable transportation, transportation by hour prevails over transportation by kilometer.

Rate

Hourly rate.

TR Activity

Transportation activity.

NOTE: Maestro* uses the transportation activity defined in Catalogue Management or the activity defined in Define Trucks as the default value.

Address

Address line 1.

Address 2

Address line 2.

Address 3

Address line 3.

Number

Identifies the company number in which the ticket will be saved. This column is effective only for the manufacturer Weightronix.

NOTE: The company number is used to find a company by Tag and the prefix for the transaction is applied.

Comment

Comment on the transaction.

Extra Code 01

Extra product 1.

NOTE: If an extra product exists, it must be accompanied by a quantity.

Extra Quantity 01

Extra quantity 1.

Extra U.P. 01

Extra 1 unit price.

NOTE: This value can be changed by maestro* if it applies discounts. The Transport options in Configuration are used to manage the source of prices.

Extra Amount 01

Extra Amount 1.

NOTE: This value can be changed by maestro* if it applies discounts. The Transport options in Configuration are used to manage the source of prices.

Extra Code n

Same as 01.

Extra Quantity n

Same as 01.

Extra U.P. n

Same as 01.

  1. Click the Validate the Table icon to ensure the integrity of the data to be imported.

 

The table must be checked if manual corrections are made to imported data.

  1. Click the Apply icon to import the data from the grid in maestro*.

Maestro* determines the Invoicing Type according to the combination of options and data received. Maestro* first checks whether the ticket is internal according to the Internal Ticket configuration in Configuration – Quarry Tickets. If the latter is Project, maestro* checks whether the value of the project received is an existing project in maestro*. If so, the project entered in the ticket is transferred to the project in maestro* during import. If the value in the Internal Ticket configuration in Configuration – Quarry Tickets is Internal Cust. and if an Internal Customer is defined, maestro* checks whether the value in the file code matches and can determine whether the ticket is internal for the customer.

The ticket is Payable if this type of invoicing is supported by the manufacturer (Neptune or SigmaSys). In all other cases, maestro* creates a Receivable ticket.

  1. Confirm the information in the ClosedDetails tab:

Field

Description

Counter

Counter number generated by maestro*.

Source

Usually corresponds to the quarry income project.

Quotation

Number of the quotation related to the ticket.

NOTE: If the DOT checkbox is checked in the quotation entered in this field, the Severence tax will not be applied when invoicing this ticket. For more information, consult the Project Management and Quarry Quotations topics.

Ticket No.

Delivery ticket number generated by the scale.

Date

Date of the ticket.

NOTE: This date is not necessarily the posting date.

Activity

Source activity or project to which the income is charged.

NOTE: The activity is displayed automatically if it is entered in Configuration.

User No.

Displays the user who entered the transaction.

Group

Income group for the activity.

NOTE: The group is displayed automatically if it is entered in Configuration.

Date Entered

Import date.

  1. ClosedMaterial section:

When material or accrued cost accounting has been performed for the ticket, it becomes impossible to modify or delete it. A mention Accrued Material Calculated or Accrued Transport Calculated appears in red under User No. or Customer P.O.

 

Field

Description

Status

Available values:

Entry

Allows the user to transfer the ticket to invoicing.

On Hold

Used to keep the ticket with the non-transferred transactions.

Non chargeable

Used to prevent invoicing of this section of the ticket.

To be validated

Used to note that the ticket must be checked before it is transferred.

Product

Product code to be invoiced.

NOTE: This product must exist in Catalogue Management.

Customer Address

The customer address is connected to the customer and is visible only if the ticket is Receivable.

Address

Shipping address.

Billing – Date

The first date field displays the invoicing posting date. The second date field displays the completion date of the invoice. These fields cannot be modified.

Comment

Description for reference purposes.

Invoicing Type

Available values:

Internal

Used to generate an invoice for an internal customer or an existing project in Project Management.

Not Applicable

Used if the Status field is set to Non chargeable.

Payable

Used to identify a ticket for which an invoice will be received from a supplier.

Receivable

Used to generate an invoice for an external customer.

Tax Code

US tax code which was calculated on the ticket. This field is visible only if the ticket is COD (collect on delivery) and the US taxes are enabled.

NOTE: Only applicable if WinTik is chosen in the Scale Software field of the Import section of the Configuration – Quarry Tickets.

Tax Amount

US tax amount which has been calculated on this ticket. This field is visible only if the ticket is COD (collect on delivery) and the US taxes are enabled.

NOTE: Only applicable if WinTik is chosen in the Scale Software field of the Import section of the Configuration – Quarry Tickets.

Quantity

Quantity of material delivered to the customer.

UP – Amount

Unit price of the product and amount (Quantity × UP).

NOTE: The price should be displayed automatically if the Product Pricing Source field is set to Maestro in Configuration – Quarry Tickets. If the price is not displayed, check whether a price is entered in Catalogue Management or Define Customer Pricing.

Surcharge

Amount that corresponds to the surcharge to invoice. Is visible if an item has been entered in the Surcharge field of Catalogue Management for the selected product.

NOTE: This field cannot be modified. To modify the value of the surcharge, access the product in the Catalogue Management option.

TR Qty

Transportation quantity to be invoiced.

NOTES: This quantity should be displayed automatically and equal the quantity of material.

This field is only available if the Carrier Type is Hired Trucker.

UP – Amount

Unit price and amount (TR Qty × UP) of the transportation.

NOTE: The price should be displayed automatically if the Rec. Transport Qty and Pricing Source field is set to UP maestro* and the Hired Truckers? field is set to YES in Configuration – Quarry Tickets. If the price is not displayed, check if a price is entered in Catalogue Management.

Company

If the Invoicing Type is set to Internal or Payable, it allows the specification of the default destination company.

Project or Customer Project

Project number or customer project number, if the Invoicing Type is Receivable.

NOTE: This field is used if the Def. Internal Ticket field is set to Project in Configuration.

Activity

Identifies the expense activity of the material if this is an internal sale.

Group

Expense group for the material if this is an internal sale.

Contract

Customer contract number.

Customer

Customer code, in the case of a Receivable ticket.

Supplier

Supplier code, in the case of a Payable ticket.

Record

Record number used for information purposes.

User No.

User number.

P.O.

Customer’s order number or internal reference number.

NOTE: This field links with the Define Customer Pricing option.

Customer P.O.

Used to specify the customer’s order number if the P.O. field has been used for other purposes.

RM Invoice

Invoice number available after invoicing.

  1. Extras section: this section is available only if the Invoicing Type is Internal or Receivable.

Field

Description

01, 02, 03 and 04

Identifies an extra added to the ticket.

NOTE: Only the 4-TKS interface can import this information.

Quantity

Quantity of the extra.

Unit Price

Unit price of the extra.

Amount

Extra amount.

  1. ClosedTransportation section:

Field

Description

Status

Available values:

Entry

Allows the user to transfer the ticket to invoicing.

On Hold

Used to keep the ticket with the non-transferred transactions.

Non chargeable

Used to prevent invoicing of this section of the ticket.

To be validated

Used to note that the ticket must be checked before it is transferred.

Type

Available values:

Internal

Used to generate an invoice for an internal customer or an existing project in Project Management.

Receivable

Used to generate an invoice for an external customer.

Standard

Used to identify a ticket for which an invoice will be received from a supplier.

Time

Delivery time. This field is used for information purposes only.

TR Qty

Amount of material transported.

Invoice No.

Invoice number.

Billing – Date

The first date field displays the invoicing posting date. The second date field displays the completion date of the invoice. These fields cannot be modified.

Region

Region from Zone Management.

Supplier

Transportation supplier from Supplier Management.

KM

Number of kilometers covered.

UP

Unit price per kilometer or per ton.

NOTE: The unit price may be from the Transportation Rates Table if completed or from a catalogue item based on Configuration.

Truck #

Truck used from Define Trucks.

NOTE: This field is required if the billing method chosen is by catalogue item.

Hours

Number of hours invoiced by the truck driver.

Rate

Truck driver’s hourly rate.

NOTE: The rate may be from the Transport Rates if completed or from the Supplier Rates option.

Amount

Cost calculated for transportation.

Project

Project number on which transportation is provided.

Activity

Identifies the transportation expense activity.

Group

Identifies the transportation expense group.

User No.

User who entered the transaction in maestro*.

TR P.O.

Purchase order number associated with the transportation.

TR Invoice

Invoice number available after invoicing.

  1. Click Save.

 

Create a ticket from a pending transaction

  1. Click on the Pending Transactions icon.
    The selection grid, at the top of the screen, displays the Quarry Tickets’ pending transactions.
  2. Select a pending transaction.
    The pending transaction’s attached files are displayed in a new window.
 

If more than one file is attached, they will be displayed in the following order: PDF, Image, Excel, and Others.

  1. The system automatically completes some entries in the options window (the user who created the transaction, the date and time of creation, etc.).
 

Other entries will automatically be completed if the transaction comes from the Import Outlook Emails option.

  1. Complete and save the transaction.
 

The transaction’s attached files will be available through the Document Management option upon saving.

 

See also

 

APPENDIX

Manufacturer's Technical Specifications

ClosedNEPTUNE

The Neptune import file is a flat file containing 31 fields. It is usually named “TRANS.TXT”. The values in the file are put between quotation marks and separated by commas. Example: “Value1”, “Value2”, etc.

The fields in the Neptune and maestro* files are matched.

 

No.

Field

Maestro* equivalent

1

Ticket No.

Ticket No.

2

VehNo

Truck Number

3

ContractNo

Contract

4

CustomerCode

File Code

5

ProjectNo

Customer Project

6

ProductCode

Product Code

7

OrderNo

Purchase Order

8

NetWeight

Quantity

9

ProdPU

Sale UP RM

10

ProdTotal

Product Amount

11

ProdTrPU

Cost UP TR

12

ProdTrKm

Km

13

ProdTrTot

Sale UP TR

14

VehPU

 

15

VehTot

 

16

DelType

 

17

TypeClass

Carrier Type

18

Addr1

Address 1

19

Addr2

Address 2

20

Zone

 

21

ES

Input/Output

22

Status

 

23

KiloType

 

24

DateTime

Transaction date

Format: ‘YYYY/MM/DD HH:MM’

25

NoCompany

Co. No.

NOTE: If there is an “X” in the Source selected in the header, it is replaced with the value in this field and assigned to the Source column.

26

Activity no. 1

Activity Expense

27

Source

Region if ES = Input

28

CustomerRegion

Region if ES = Output

29

Activity no. 2

TR Activity

30

Order No

Customer P.O.

31

Comment

Comment

ClosedWEIGHTRONIX

The Weightronix import file is a flat file with 24 fields. The values in the file are put between quotation marks and separated by commas. Example: “Value1”, “Value2”, etc.

The first two lines contain information about how the file is generated and are ignored by maestro*.

 

No.

Field

Maestro* equivalent

1

Ticket No.

Ticket No.

2

VehNo

Truck Number

3

ContractNo

Contract and Customer Project

4

CustomerCode

File Code

5

ProjectNo

6

ProductCode

Product Code

7

OrderNo

Purchase Order

8

NetWeight

Quantity

9

ProdPU

Sale UP RM

10

ProdTotal

Product Amount

11

ProdTrPU

Cost UP TR

12

ProdTrKm

Km

13

ProdTrTot

Sale UP TR

14

 

15

 

16

 

17

TypeClass

Carrier Type

NOTE: This manufacturer uses 1 for Hired Trucker. All of the remaining values refer to the Customer Driver.

18

Addr1

Address 1

19

Addr2

Address 2

20

Zone

Region

21

ES

Input/Output

22

Status

If this value contains an * character, the Import box is checked.

23

 

24

DateTime

Transaction date

Format: ‘YYYY.MM.DD HH:MM:SS’

ClosedBOURBEAU SCALE

The Balance Bourbeau import file is a flat file with 8 fields. The values in the file are put between quotation marks and separated by commas. Example: “Value1”, “Value2”, etc.

This manufacturer only manages receivable tickets and the Customer Driver carrier type.

 

No.

Field

Maestro* equivalent

1

CustomerCode

File Code

2

Date

Date

Format: ‘YYYYMMDD’

3

Contract

Customer Project

4

Ticket No.

Ticket No.

5

ProductCode

Product Code

6

Qty

Quantity

7

UP

UP Sale

8

Dest.

Address 1

ClosedTKS/BILLAUT

The TKS/Billaut import file is a flat file with 43 fields. This manufacturer supports extras. The values in the file are put between quotation marks and separated by commas. Example: “Value1”, “Value2”, etc.

The first line contains a description of the fields, which is ignored by maestro*.

 

No.

Field

Maestro* equivalent

1

TICKET NO.

Ticket No.

2

NOTRUCK

Truck Number

3

CONTRACTNO

Contract

4

CUSTOMERCODE

File Code

5

PROJECTNO

Customer Project

6

PRODUCTCODE

Product Code

7

ORDERNO

Purchase Order

8

NETWEIGHT

Quantity

9

PRODPU

Sale UP RM

10

PRODTOTAL

Product Amount

11

PRODTRKM

Km 

12

PRODTRTOT

Sale UP TR

13

14

PRODTRPU

 Cost UP TR

15

 

16

 

17

TYPECLASS

Carrier Type

18

19

ADDR1

Address 1

20

ADDR2

Address 2 

21

ZONE

Region

22

ES

Input/Output 

23

STATUS

 

24

 

25

DATETIME

Date

Format: ‘YYYY-MM-DD HH:MM:SS’

26

NOCOMPANY

Co. No.

NOTE: If there is an “X” in the Source selected in the header, it is replaced with the value in this field and assigned to the Source column.

27

28

EXTRACODE01

Extra code 01

29

EXTRAQUANTITY01

Extra quantity 01

30

EXTRAUP01

Extra U.P. 01

31

EXTRAAMOUNT01

Extra Amount 01

31

EXTRACODE02

Extra code 02

33

EXTRAQUANTITY02

Extra quantity 02

34

EXTRAUP02

Extra U.P. 02

35

EXTRAAMOUNT02

Extra Amount 02

36

EXTRACODE03

Extra code 03

37

EXTRAQUANTITY03

Extra quantity 03

38

EXTRAUP03

Extra U.P. 03

39

EXTRAAMOUNT03

Extra Amount 03

40

EXTRACODE04

Extra code 04

41

EXTRAQUANTITY04

Extra quantity 04

42

EXTRAUP04

Extra U.P. 04

43

EXTRAAMOUNT04

Extra Amount 04

ClosedWINTIK

The Wintik import file is a flat file with 55 fields. The values in the file are separated by chr(9). Example: Value1 Value2, etc.

This manufacturer only supports output tickets, which are receivables.

 

No.

Field

Maestro* equivalent

1

COMPANY

Co. No.

2

LOCCODE

3

TICKNUM

Ticket No.

4

TICKDATE

Date

Format: ‘YYYYMMDD HH:MM:SS’

5

TICKSTATUS

The tickets are only imported into the grid if the TICKSTATUS field contains A.

6

TRUCKCODE

Truck Number

7

TRUCKTYPE

8

QUOTENUM

9

CHARGETOFLAG

10

CUSTCODE

File Code

11

JOBCODE

Customer Project and Contract

12

EQCODE

13

ORDERNUM

Purchase Order

14

ZONECODE

Region

15

SHIPTO1

Address 1

16

SHIPTO2

Address 2

17

SHIPTO3

Address 3

18

PRODCODE

Product Code

19

PRODDESC

20

PRODSTDUNIT

21

PRODSALEUNIT

22

GROSSWEIGHT

23

TAREWEIGHT

24

NETWEIGHT

25

STDWEIGHT

Quantity

26

SALEWEIGHT

27

CASHSALE

28

MINQTYPRODUCT

29

PRODUNITPRICE

Sale UP RM

30

PRODSALEAMOUNT

Product Amount

31

HAULMETHOD

Carrier Type

NOTE: If the value is H or O, maestro* uses Hired Trucker. If not, Customer Driver is used.

32

MINHAULFLAG

33

HAULQTY

Sale UP QTY

34

HAULUNITPRICE

Cost UP TR

35

HAULUNITCOST

36

PRODTAX1AMOUNT

37

PRODTAX2AMOUNT

38

HAULTAX1AMOUNT

39

HAULTAX2AMOUNT

40

TOTALSALE

41

SPARE1

42

SPARE2

43

SPARE3

44

SPARE4

45

UPDATED

46

PRICEOVERRIDE

47

TICKETWEIGHTUOM

48

JOBACCOUNT

Activity for the expense

49

JOBCOSTTYPE

50

OPERATOR

51

TRUCKOVERLOADED

52

RAMORDER

53

MTOITEM

54

MANUALWEIGHT

55

DRIVERCODE

56

INVOICE

57

HAULSALEAMOUNT

58

SHIPPED_PRODUCT_CODE

59

WSTICK_SITE_CODE

60

LEVY_AMOUNT

61

WSTICK_LAST_MODIFIED

62

WSTICK_LAST_MODIFIED_SITE

63

LEVY_QTY

64

LEVY_RATE

65

LEVY_UOM

66

LEVY_TAX1_AMOUNT

67

LEVY_TAX1_AMOUNT

68

WSORDERS_GUID

69

WSORDDET_LINE_NUMBER

70

ROWGUID

71

TAXCODE

72

CUSTOMER_SITE_CODE

73

CUSTOMER_PHASE

74

CUSTOMER_LOT

75

KM

Km

ClosedSIGMASYS

The SigmaSys import file is an XML file. This manufacturer supports extras.

The Carrier Type is set to Customer Driver by default.

Three methods can be used to supply extras: Fixed amount, Amount per ton or Percentage (not supported by maestro*).

 

LEVEL01

LEVEL02

Maestro* equivalent

NO_TRANSACTION

Ticket No.

NO_COMPANY

Co. No.

NOTE: If there is an “X” in the Source selected in the header, it is replaced with the value in this field and assigned to the Source column.

INPUT_OUTPUT

Input/Output

DATE

Date

Format: ‘YYYYMMDD’

TIME_ENTERED

TIME_OUT

NO_CUSTOMER

File Code

NO_PROJECT

Customer Project

NO_SITE

NO_SUPPLIER

NO_PRODUCT

Product Code

NO_DRIVER

NO_ZONE

Region

NO_CONTRACT

Contract No

NO_CUSTOMER_ORDER

Purchase Order Customer

NO_PURCHASE_ORDER

Purchase Order

NO_INVOICE

NO_TRANSPORT_BILL

NO_CARRIER

NO_VEHICLE

DESCRIPTION

NO_TRAILER

NO_TRAILER2

GROSS

TARE_VEHICLE

TARE_TRAILER

NET

NET_CHARGE

Quantity

MAXIMUM_WEIGHT

SURCHARGE

UNIT_WEIGH

MODE_GROSS

MODE_TARE_VEHICLE

MODE_TARE_TRAILER

MILEAGE

KM

UNIT_PRICE

Sale UP RM

UNIT_PRICE_UNIT

PRICE

MP sale amount

DISCOUNT_AMT

TOTAL_ADD_EXPENSE

SUB_TOTAL

GST

PST

TOTAL

CURRENCY

APPLY_MIN_AMOUNT

TRANSPORT_EXPENSE_METHOD

PAYMENT_STATUS

DATE_CANCELLATION

DATE_PRINTING

DATE_MODIFICATION

DATE_TRANSFER

NO_PLANT

COMMENTS

NOTES

NO_REGISTRATION_VEHICLE

Truck Number

NO_REGISTRATION_TRAILER

NO_REGISTRATION_TRAILER2

TRANSPORT_EXPENSE_TONNAGE

Sale UP QTY

UNIT_PRICE_TRANSPORT_EXPENSES

Cost UP TR

TRANSPORT_EXPENSE_AMOUNT

Sale UP TR

ADDITIONAL_EXPENSE_LINE

NO_LINE

CODE

Extra 0X code

DESCRIPTION

FIXED_AMOUNT

Extra 0X quantity set to “1”. U.P. Extra 0X set to Extra 0X Amount.

PERCENTAGE

Not supported

AMOUNT_TON

Extra 0X quantity

AMOUNT

Extra 0X amount

 

Last modification: November 19, 2024